home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #14
/
Monster Media No. 14 (April 1996) (Monster Media, Inc.).ISO
/
bbs_door
/
pray101.zip
/
PRAYER.DOC
< prev
next >
Wrap
Text File
|
1996-02-17
|
7KB
|
163 lines
PRAYER LINE Version 1.01 Feb 17,1996
Christian One Liner
Ken Kirkley - Glory Bound BBS - 864-592-5208
Mail Networks: FIDONet 1:3652/5; FMLYNet 8:8301/3
Magic Name for FREQ'ing - PRAYER
-------------------------------------------------------------------------
SYSTEM REQUIREMENTS
PRAYER LINE has been written in Turbo Pascal and compiled with Assembly
Language serial input/output routines for maximum speed. It fully
supports high speed modems: 16550 FIFO buffering and locked serial ports.
This BBS door game is DesqView, Windows, and OS/2 aware. It will support
all of the most popular door data file formats: TriBBS, PCBoard,
GAP (DOOR.SYS), Spitfire, WildCat!, RBBS, and WWIV. Thus, a door that
is built around compatability with a wide range of BBS software.
**In order to use the DOWNLOAD feature of PRAYER LINE, be sure you have
a copy of DSZ.EXE in your PATH statement or within the directory you
run PRAYER LINE from.
-------------------------------------------------------------------------
PROGRAM USAGE
[1] UNZIP the file into your BBS door directory of your choice. READ
the DOC files carefully!
[2] EDIT the enclosed config file (PRAYER.CFG) or create your own
config file using the example below. This is how I run PRAYER LINE
with ProBoard BBS.
GAP
C:\PB\NODE1
Glory Bound BBS
Ken Kirkley
38400
[3] This BBS door game is run by entering a command line similar to the
following:
PRAYER PRAYER.CFG (door config)
In the above command line, "PRAYER" is the name of the door's EXE
file and the "PRAYER.CFG" parameter is the name of the door's
configuration file. The configuration file can have any name the
sysop chooses, but it must reside in the same directory as the door.
The configuration file is an ASCII text file with the following
format:
Line 1: Door data file type.
Line 2: Path to the door data file(s).
Line 3: BBS name.
Line 4: Sysop's name.
Line 5: Locked baud rate.
Following is an example of the BAT file I use to run PRAYER LINE
under ProBoard BBS software.
:PRAYER
cd\doors\prayer
prayer prayer%2.cfg
cd\pb\node%2
GOTO END
As illustrated above, the door's data file type is specified in
line 1 and can be PCB for PCBoard, GAP for GAP (DOOR.SYS), SF for
Spitfire, RBBS for RBBS, WC for WildCat!, TRIBBS for TriBBS, or WWIV
for WWIV. The locked baud rate is specified in line 5. If the sysop
doesn't lock his serial port, he must specify 0 for the locked baud
rate.
NOTE: Although many door formats do pass the locked baud rate in the
door data files, some older formats such as RBBS do not. For
conformity, PRAYER LINE requires that you specify the locked baud
rate in line 5 and ignores any value passed in the door data files.
Nonstandard IRQs can be used with PRAYER LINE by specifying the IRQ
number after the "config" parameter in the command line used to run
the door as follows: PRAYER PRAYER.CFG IRQ
[4] LOCAL MODE: PRAYER LINE can be run locally without a door data file
(handy for the sysop to use the door without logging on to the BBS)
by specifying /L after the configuration file parameter in the DOS
command line. PRAYER LINE will request the user to enter his name
before running the door.
Example: PRAYER PRAYER.CFG /L
[5] SPECIAL KEYS: While a door is running, the sysop can press certain
special keys to perform a variety of functions. The following is a
list of the functions that the PRAYER LINE special keys perform:
Key(s) Function
HOME Toggles between the user status window and a help
display that lists the door special keys.
F6 Takes 5 minutes away from the caller.
NOTE: This will NOT be returned to BBS.
F7 Gives 5 minutes to the caller.
NOTE: This will NOT be returned to the BBS.
F9 Quit the door and return the caller to the BBS.
F10 Enter chat mode. Pressing the ESC key exits the
chat mode.
Alt+D Drop to DOS.
-------------------------------------------------------------------------
MULTI-NODE EXAMPLES
PRAYER LINE should support the multi-node feature. FIRST, you must have
the program SHARE.EXE run from your AUTOEXEC.BAT FILE! If you do NOT
have this installed, prior to running the BBS, it will NOT work! It is
easy to config the game for this. Just make TWO or MORE config files,
with different names, and call the program from the batch file that you
use for the doors in your BBS. Here is a small example:
Call the door config file for node 1: PRAYER1.CFG
Call the door config file for node 2: PRAYER2.CFG
Run in your batch files like this:
Node 1 - PRAYER PRAYER1.CFG
Node 2 - PRAYER PRAYER2.CFG
-------------------------------------------------------------------------
WARRANTY AND DISCLAIMER
PRAYER LINE is distributed without warranty. In no event will Ken
Kirkley be liable to you for damages, including any loss of profits, lost
savings, or other incidental or consequential damages arising out of your
use of or inability to use the program, even if Ken Kirkley or an
authorized representative has been advised of the possibility of such
damages. Ken Kirkley will not be liable for any such claim by any other
party. PRAYER LINE is only guaranteed to take up room on your disk.
There are no warranties, either expressed or implied, with respect to the
software, its quality, performance, usefulness, or fitness for any
particular purpose. This software is provided "AS IS" and the entire
risk as to its quality and performance is with the user. The author of
this software shall not be liable for errors contained in the software or
the software's documentation, or for incidental or consequential damages
of any kind in connection with the performance, use, or possession of
this software.
-------------------------------------------------------------------------
CREDITS
This program was compiled using RMDoor by Randy Hunt and Mark Goodwin.
Turbo Pascal is a registered trademark of Borland International
MS-DOS is a registered trademark of Microsoft Corporation
All other programs are copyright and/or trademarked by their respective
authors unless otherwise noted.
------------------------------End Of Doc---------------------------------